Method for encrypting transactions at a dynamic transaction card

ABSTRACT

One variation of a method for controlling a dynamic transaction card includes: at a first time, accessing a first cryptogram; at a second time, establishing a wireless connection with a mobile computing device; in response to establishing the wireless connection with the mobile computing device, accessing a first token associated with the first cryptogram from the mobile computing device via the wireless connection; generating a first magnetic stripe sequence command representing the first cryptogram and the first token; and in response to detecting a magnetic stripe card reader proximal a magnetic stripe emulator integrated into the dynamic transaction card at a third time succeeding the second time, driving the magnetic stripe emulator according to the first magnetic stripe sequence command.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/360,844, filed on 11 Jul. 2016, which is incorporated in its entiretyby this reference.

This application is a continuation-in-part application of U.S. patentapplication Ser. No. 15/016,582, filed on 5 Feb. 2016, which is acontinuation of U.S. application Ser. No. 13/904,951 filed on 29 May2013, which claims the benefit of U.S. Provisional Application No.61/689,083 filed on 29 May 2012, U.S. Provisional application No.61/796,594, filed on 15 Nov. 2012, U.S. Provisional Application No.61/848,581 filed on 7 Jan. 2013, U.S. Provisional Application No.61/849,213 filed on 22 Jan. 2013, U.S. Provisional Application No.61/850,866, filed on 25 Feb. 2013, and U.S. Provisional Application No.61/818,831, filed on 2 May 2013, all of which are incorporated herein intheir entireties by this reference.

This application is a continuation-in-part application of U.S. patentapplication Ser. No. 14/542,092, filed on 14 Nov. 2014, which claims thebenefit of U.S. Provisional Patent Application No. 61/962,709 filed on14 Nov. 2013, and U.S. Provisional Patent Application No. 62/003,430,filed on 27 May 2014, all of which are incorporated in their entiretiesby this reference.

This application is a continuation-in-part application of U.S. patentapplication Ser. No. 13/904,939, filed on 29 May 2013, which isincorporated in its entirety by this reference.

TECHNICAL FIELD

This invention relates generally to the field of transactional cardsand, more specifically, to a new and useful for method for encryptingtransactions at a dynamic transaction card in the field of transactionalcards.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a flowchart representation of a method;

FIG. 2 is a flowchart representation of the method;

FIG. 3 is a flowchart representation of the method;

FIG. 4 is a flowchart representation of the method;

FIG. 5 is a flowchart representation of the method;

FIG. 6 is a flowchart representation of the method;

FIG. 7 is a flowchart representation of the method;

FIG. 8 is a flowchart representation of the method;

FIG. 9 is a flowchart representation of the method;

FIG. 10 is a flowchart representation of the method;

FIG. 11 is a flowchart representation of the method; and

FIG. 12 is a flowchart representation of the method.

DESCRIPTION OF THE EMBODIMENTS

The following description of embodiments of the invention is notintended to limit the invention to these embodiments but rather toenable a person skilled in the art to make and use this invention.Variations, configurations, implementations, example implementations,and examples described herein are optional and are not exclusive to thevariations, configurations, implementations, example implementations,and examples they describe. The invention described herein can includeany and all permutations of these variations, configurations,implementations, example implementations, and examples.

1. First Method

As shown in FIGS. 1-4, a method S100 for encrypting transactions at adynamic transaction card includes: at a first time, accessing a firstcryptogram in Block S110; at a second time, establishing a wirelessconnection with a mobile computing device in Block S120; in response toestablishing the wireless connection with the mobile computing device,accessing a first token associated with the first cryptogram in BlockS130; generating a first magnetic stripe sequence command representingthe first cryptogram and the first token in Block S140; and in responseto detecting a magnetic stripe card reader proximal a magnetic stripeemulator integrated into the dynamic transaction card at a third timesucceeding the second time, driving the magnetic stripe emulatoraccording to the first magnetic stripe sequence command in Block S150.

2. Applications

Generally, as shown in FIG. 1, the method S100 can be executed on areprogrammable (e.g., “dynamic”) transaction card—such as described inU.S. patent application Ser. No. 13/904,939—to emulate various tokenizedtransactions methods (e.g., a credit card, a debit card, etc.) in onephysical card by selectively broadcasting tokens and cryptograms for aselected transaction (or payment) method over radio-frequencycommunication protocol or via a magnetic stripe emulator.

The dynamic transaction card is preprogrammed (e.g., during manufacture)with a static cryptogram (or a set of static cryptograms or a cryptogramgenerator) and an identifier (e.g., a serial number, a Bluetoothaddress). Once the dynamic transaction card is acquired by a user, theuser can link the dynamic transaction card to a native application(e.g., smartphone “app” or browser-based application) executing on hismobile computing device (e.g., smartphone, tablet), such as by theidentifier programmed into the dynamic transaction card. The user canthus “load” transaction methods—such as credit cards, debit cards, giftcards, door access cards, personal identification cards, rewards cards,etc.—onto the dynamic transaction card via the native application. Forexample, the user can manually enter a credit card number, expirationdata, CVV, billing address, and owner's name into an interface withinthe native application.

Alternatively, the user can capture an image of a credit card with acamera integrated into the mobile computing device, and the nativeapplication can implement optical character recognition methods andtechniques to extract relevant credit card information from the image.Yet alternatively, the user can link a transaction account related tothe credit card to the native application (e.g., a credit card account),and the native application can retrieve relevant transaction data forthe credit card from the transaction account (e.g., hosted by athird-party issuer or token generator). However, the user can linktransaction methods to the user's native application in any othersuitable way.

In one implementation, the native application generates a magneticstripe sequence command from credit card data thus entered directly intothe native application or retrieved by the native application. Thenative application can then upload this magnetic stripe sequence commandto the dynamic transaction card for emulation by the magnetic stripeemulator within the dynamic transaction card during a subsequenttransaction. As shown in FIG. 2, the native application also manipulatesthese credit card data to retrieve, from a remote server (i.e.,affiliated with a token generator), a transaction token corresponding tothe credit card. For example, the native application can retrieve thetransaction token representing an encrypted credit card number and/orcredit card account information. The native application can then uploadthe transaction token to the dynamic transaction card for broadcast bythe radio-frequency wireless transmitter within the dynamic transactioncard during a subsequent transaction.

In an alternative implementation, the native application manipulatescredit card data thus collected to retrieve from a remote server atransaction token corresponding to the credit card and then uploads thetransaction token to the dynamic transaction card. In thisimplementation, the dynamic transaction card associates the transactiontoken with a cryptogram pre-loaded onto the dynamic transaction card,such as a by manufacturer of the dynamic transaction card or by aprocessing house seeding the dynamic transaction card with thecryptogram. Then the dynamic transaction card can transform thetransaction token and the (pre-loaded) cryptogram into a magnetic stripesequence command. The dynamic transaction card can then drive themagnetic stripe emulator according to the magnetic stripe sequencecommand when a magnetic stripe card reader is detected near the dynamictransaction card. In this implementation, the radio-frequency wirelesstransmitter similarly broadcasts a form of the transaction token and thenew cryptogram when a wireless transaction reader (e.g., a near-fieldcommunication reader) is detected near the dynamic transaction card.

In the foregoing implementations, a tokenized transaction method can beenabled on the dynamic transaction card by routing a token—for a newtransaction method loaded into the native application executing on theuser's computing device—from a remote server (e.g., a token generator),through the mobile computing device, to the dynamic transaction card, asshown in FIG. 2. (Alternatively, the dynamic transaction card cangenerate the token via a token generator stored locally on the dynamictransaction card, wherein outputs of the local token generator on thedynamic transaction card are known by a select external entity—such asthe affiliated financial institution or an authentication server—toauthenticate a transaction with the dynamic transaction card based onalignment between a token and cryptogram received from the dynamictransaction card at a POS system.) The dynamic transaction card can thenassociate the token with a cryptogram (e.g., a static cryptogrampreloaded onto the dynamic transaction card with a new cryptogramgenerated by a cryptogram generator programmed into the dynamictransaction card), such as by generating a magnetic stripe sequencecommand representing the token and the cryptogram. The dynamictransaction card can then emulate the corresponding transaction methodby transmitting a form of the token and the cryptogram via the magneticstripe emulator and/or via the radio-frequency transmitter. Thus, thedynamic transaction card can execute the method S100 to emulate aparticular tokenized transaction method in magnetic stripe-basedtransactions and/or in radio-frequency-based transactions selectively asneeded, such as based on local availability of a wireless transactionreader and a magnetic stripe card reader to read transaction method datafrom the dynamic transaction card. The dynamic transaction card canfurther execute the method S100 to similarly and selectively emulatevarious tokenized transaction methods in both radio-frequency-basedtransactions and in magnetic stripe-based transactions over time.

In one implementation, a first financial institution (e.g., a creditcard company) sponsors manufacture and distribution of the dynamictransaction card, which may be characterized by production costssignificantly greater than standard magnetic stripe credit cards and maybe configured to emulate an encrypted credit card through a dynamicmagnetic stripe emulator. Once issued to a user, the dynamic transactioncard can communicate encrypted payment-related information tomagnetic-stripe-type point of sale (hereinafter “POS”) systems atvendors in exchange for goods and services on behalf of the user,thereby yielding improving security and reduced risk of fraud—related tostandard magnetic stripe credit cards—for the financial institution. Forexample, during a transaction, the dynamic transaction card can emulatethrough the magnetic stripe emulator a particular cryptogram (preloadedon the dynamic transaction card) and a token representing accountinformation of the virtual credit card issued by the first financialinstitution.

Additionally, the dynamic transaction card can be configured to emulatevirtual credit cards issued by other (e.g., competitor) financialinstitutions. In this example, the dynamic transaction card can beconfigured to emulate a virtual encrypted credit card issued by a firstfinancial institution that subsidized manufacture and distribution ofthe dynamic transaction card. However, upon receipt and authorization ofthe dynamic transaction card by a user within an account in thefinancial institution, the user can load other non-encrypted creditcards and other transaction cards (e.g., loyalty cards) onto the dynamictransaction card for emulation during subsequent transactions. However,because the dynamic transaction card supports emulation of an encryptedpayment method(s) authorized by the financial institution that issuedthe dynamic transaction card, this encrypted payment method may becomethe user's default payment method when making in-person purchases fromvendors with the dynamic transaction card despite availability of otherpayment methods from other financial institutions also loaded onto thedynamic transaction card, which may provide the issuing financialinstitution greater leverage over its competitors and enable the issuingfinancial institution an opportunity to recover the cost of issuing thedynamic transaction card to the user.

Alternatively, multiple financial institutions may subsidize the dynamictransaction card; and the dynamic transaction card can be configured toemulate encrypted transaction methods (e.g., virtual credit cards and/orvirtual debit cards) issued by each of these financial institutions,such as with one common or multiple unique cryptograms loaded onto thedynamic transaction card during its manufacture.

Additionally, as shown in FIG. 7, the issuing financial institution mayremotely and immediately (e.g., nearly instantaneously) issue areplacement virtual credit card to the dynamic transaction card, such asover a computer network (e.g., the Internet) and via the user'ssmartphone when fraud or other issues with the user's payment accountare detected. For example, in response to detecting fraud associatedwith a credit card or other transaction account issued to a user andloaded onto the user's dynamic transaction card, a financial institutionaffiliated with the credit card account may “replace” the credit cardaccount by issuing a new virtual credit card to the user's account. Thedynamic transaction card can instantiate the new virtual credit card foruse as a physical transaction (e.g., credit) card by receiving a newtoken from a token generator—local or remote from the dynamictransaction card—associated with the new virtual credit card. Forexample, the dynamic transaction card can instantiate the new virtualcredit card for use as a physical transaction card through the dynamictransaction card by marrying a new token (or token generator)representing the new virtual card with a cryptogram (or cryptogramgenerator) stored on the dynamic transaction card to generate a newmagnetic stripe sequence command that, when output by the magneticstripe emulator, may be authenticated by a payment processor, financialinstitution, or other authentication server to complete payment with thevirtual credit card. Alternatively, the dynamic transaction card caninstantiate the new virtual credit card for use as a physicaltransaction card through the dynamic transaction card by merging PAN orother data representing the new virtual credit card with a token orcryptogram stored locally on the dynamic transaction card or in thenative application to generate a new magnetic stripe sequence command.

The dynamic transaction card can also receive a graphical representationof the new virtual credit card that, when rendered within the nativeapplication executing on the user's smartphone, communicates to the userthat her credit card has been replaced. Thus, the financial institutionmay avoid mailing a new physical credit card to the user, which mayotherwise be inconvenient for the user and result in reduced use of thecredit card by the user.

3. Terms and Definitions

As shown in FIGS. 3 and 4, Blocks of the method S100 can be executed bya dynamic transaction card issued to a user and a native applicationexecuting on the user's mobile computing device (e.g., smartphone,smartwatch) to emulate magnetic stripe sequences of virtual transactioncards issued to the user from one or more financial institutions.Generally, the method S100 can be implemented to conceal sensitivetransaction information (e.g., account numbers, account holderinformation, CVV, etc.) before, during, and after financial transactionsat points of sale. In particular, Blocks of the method S100 can beimplemented by the dynamic transaction card and the native applicationto output encrypted payment information to a POS system configured tootherwise (only) accept magnetic stripe data, thereby reducing risk ofhacking, fraudulently spoofing, or other fraudulent use of dataintercepted from the POS system (or from the dynamic transaction carditself, the native application, etc.)

In one implementation, a mobile computing device (e.g., a smartphone ortablet) wirelessly connected to the dynamic transaction card cooperateswith a financial institution—such as a bank, a credit union, a creditcard company, a loyalty rewards program host, etc.—to download accountinformation for a transaction method (e.g., a credit card, a debit card,a loyalty card, etc. affiliated with a user's financial account) fromthe financial institution and stores this account information in localmemory on the mobile computing device.

During manufacture of a dynamic transaction card, a dynamic transactioncard manufacturer may load a static cryptogram (or a set of staticcryptograms or a cryptogram generator) onto the dynamic transactioncard, wherein each cryptogram preloaded onto the dynamic transactioncard functions as a unique encrypted identifier of the dynamictransaction card. The dynamic transaction card manufacturer can issue alog linking a set of dynamic transaction cards produced by the dynamictransaction card manufacturer to unique cryptograms loaded onto thesedynamic transaction cards. Additionally or alternatively, the dynamictransaction card manufacturer can issue a log (or registry) ofcryptograms output by the cryptogram generator stored locally on thedynamic transaction card; a payment processor and the financialinstitution can cooperate to authenticate a transaction with the dynamictransaction card based on alignment between a token and cryptogramreceived during the transaction and based on an expected cryptogram, asindicated in the log.

The financial institution (and/or the dynamic transaction cardmanufacturer) can then send the dynamic transaction card to a user(i.e., an account holder at the financial institution), such as via aphysical mail service. Upon receipt of the dynamic transaction card, theuser may trigger the dynamic transaction card to wirelessly pair to hersmartphone. Through a native application executing on her smartphone,the user may then request authorization of the dynamic transaction card,such as by logging in to her financial account—hosted by the financialinstitution—within the native application.

In response to a request to authorize the card—such as including aunique identifier of the dynamic transaction card, the cryptogram loadedonto the dynamic transaction card, and/or login information entered bythe user within the native application—received from the user via thenative application, the financial institution may: identify the dynamictransaction card based on the log described above; confirm a matchbetween the dynamic transaction card and the account informationprovided by the user; and query a token generator to generate a token(e.g., an encrypted representation of sensitive account information,such as a credit card number) if the cryptogram, dynamic transactioncard, and user account information match. The token generator can thenreturn this token to the mobile computing device via the Internet. Uponreceipt of the token, the native application can: visually indicate tothe user that the dynamic transaction card has been authorized; storethe token in local memory on the mobile computing device and upload thetoken to the dynamic transaction card immediately before a transactionwith a POS system; or transmit the token to the dynamic transaction cardimmediately for local storage on the dynamic transaction card.(Alternatively, the dynamic transaction card can be loaded with a tokengenerator integrated into the dynamic transaction card. The tokengeneration can generate a single-use or multi-use token for emulationduring a transaction method.)

Upon receipt of the token, the dynamic transaction card can associatethe token with the cryptogram, such as by compiling these data into amagnetic stripe sequence command thereby correlating the transactionmethod represented by the token with a unique identifier of the dynamictransaction card. Subsequently, in response to detecting a magneticstripe card reader of a POS system proximal the dynamic transactioncard, the dynamic transaction card (e.g., a controller in the dynamictransaction card) can drive the magnetic stripe emulator according tothe magnetic stripe sequence command, thereby communicating both thecryptogram and the token to the POS system. The POS system can thentransmit these encrypted data to a payment processor, which interfaceswith the token generator and/or the financial institution toauthenticate these encrypted data as a proper token and cryptogram pairbefore debiting and crediting of the user's account and the merchant'saccount to complete the transaction. (However, in response to receipt ofthe token exclusively (i.e., without the cryptogram) or receipt of thetoken with a different cryptogram, the payment processor may flag thetransaction as fraudulent or otherwise unexpected.)

However, the financial institution, token generator, and/or paymentprocessor may authorize encrypted transactions and issue payment forencrypted transactions affiliated with a particular transaction methodin any other way.

Furthermore, the dynamic transaction card, as described below, canaccept and emulate multiple other transaction methods (e.g., paymentmethods, loyalty rewards programs)—unaffiliated with the same financialinstitution—in addition to the (primary) transaction method describedabove. However, the dynamic transaction card can transmit unencrypted(raw) account information representing these other transaction methodsto POS systems during other transactions in which these transactionmethods are selected by the user for emulation, as described below.

4. Dynamic Transaction Card

As described in U.S. patent application Ser. No. 13/904,939 and shown inFIGS. 2A, 2B, and 2C, the dynamic transaction card can include: a sheet;a transducer arranged within the sheet and configured to output avoltage in response to an impulse on a surface of the sheet; a wirelesscommunication module; a first input region adjacent the first icon; asecond input region adjacent the second icon; a magnetic stripeemulator; a magnetic stripe card reader sensor configured to detect amagnetic stripe card reader proximal the dynamic transaction card; and acontroller arranged within the sheet and configured to transition from apassive state (e.g., an inactive mode, an off state, a sleep state) intoan active mode (e.g., a payment mode) in response to receiving a voltageoutput from the transducer. The controller can also be configured toreceive a first token with a first transaction method and a second tokenassociated with a second transaction method through the wirelesscommunication module, and to selectively drive the magnetic stripeemulator to emulate the first token and to emulate the second tokenbased on a selection of the first and second transaction methods and inresponse to detecting a magnetic stripe card reader proximal the sheet.

The dynamic transaction card can also include: (local) memory storing acryptogram (and/or a cryptogram generator) and a token corresponding toa transaction method loaded on the dynamic transaction card; aradio-frequency transmitter or other transmitter and/or receiverconfigured to broadcast a cryptogram and a form of a token of a selectedtransaction method in response to detection of a radio-frequency cardreader proximal the dynamic transaction card; and/or a biometric sensorconfigured to read a fingerprint from a user and to authenticate use ofthe dynamic transaction card in a subsequent transaction based on thefingerprint.

Generally, the dynamic transaction card functions to consolidatemultiple plastic transaction cards into a single physical card that canimitate payment functionalities of the multiple plastic transactioncards by selectively broadcasting signals from a magnetic stripeemulator and/or a radio-frequency transmitter integrated into thedynamic transaction card. For example, the dynamic transaction card canimitate a user's debit card issued through a bank, a user's primarycredit card issued by a preferred credit card company, and a user'ssecondary credit card issued by another credit card company byselectively driving the magnetic stripe emulator—both through themagnetic stripe emulator—according to a token assigned to each of thetransaction methods and a cryptogram assigned to the dynamic transactioncard. The dynamic transaction card can also imitate a gift card, anidentification (i.e., ID) card (e.g., a driver's license), a loyaltycard (e.g., for a loyalty rewards program), a door or gate access card,or any other magnetic stripe-based and/or tokenized transaction card.

As described below, the dynamic transaction card can include multiple“payment slots,” each holding data (e.g., a magnetic stripe sequencecommand) pertaining to a particular transaction method loaded onto thedynamic transaction card. For example, a “first payment slot” on thedynamic transaction card can “hold” (e.g., point to) a tokencorresponding to a credit card and a cryptogram identifying the “firstpayment slow”; a “second payment slot” on the dynamic transaction cardcan hold a token corresponding to a debit card and a cryptogramidentifying the “second payment slow”; and a “third payment slot” on thedynamic transaction card can hold unencrypted transaction informationcorresponding to a gift card. A user can thus select one of the first,second, and third slots on the dynamic transaction card (e.g., byselecting a corresponding input region on the dynamic transaction card,as described in U.S. patent application Ser. No. 13/904,939, or byselecting a corresponding notification on a mobile computing devicewirelessly connected to the dynamic transaction card, as described inU.S. patent application Ser. No. 14/542,092) to set the dynamictransaction card to emulate the correspond transaction method in anupcoming transaction. Subsequently, the dynamic transaction card candrive the magnetic strip emulator according to a magnetic stripesequence command, corresponding to a token for the selected transactionmethod and a cryptogram, when the dynamic transaction card is swept pasta magnetic stripe card reader (e.g., a magnetic stripe card reader). Theradio-frequency transmitter can broadcast a form of the token for theselected transaction method and the cryptogram when the dynamictransaction card is tapped on or otherwise brought within wirelesscommunication range of a wireless transaction reader (e.g., an NFCreader). The dynamic transaction card can also interface with a mobilecomputing device to download new transaction method data to paymentslots on the dynamic transaction card, to delete transaction method datafrom the dynamic transaction card, to control transaction card functionsasynchronously or in real-time, to authenticate an upcoming transaction,etc.

Furthermore, the dynamic transaction card can define a form factorsubstantially similar to that of a standard plastic transaction card,that is, 3.370″ (850.60 mm) wide by 2.125″ (53.98 mm) tall by 0.06″thick.

5. Cryptogram Generation

Block S110 of the method S100 recites, at a first time, accessing afirst cryptogram. Generally, Block S110 of the method functions to loada cryptogram—representing an encrypted identifier of the dynamictransaction card—onto the dynamic transaction card and store thecryptogram in local memory of the dynamic transaction card.

In one implementation, an external third party (e.g., a processinghouse, manufacturer, or financial institution) can generate a staticcryptogram and preload this cryptogram onto the dynamic transactioncard, such as during its manufacture. For example, a cryptogram caninclude a unique and encrypted identifier—such as an alphanumeric cardaddress, an encrypted card number, and/or a binary bit sequenceidentifier—corresponding to and identifying a dynamic transaction card.During a transaction, the dynamic transaction card can output a magneticsequence that represents the cryptogram in lieu of an unencrypted staticidentifier of the dynamic transaction card itself (e.g., the dynamictransaction card's serial number or wireless address) in order tofurther obscure the dynamic transaction card and the identity of itsowner.

Alternatively, as described below, the dynamic transaction card can bepreloaded with a local cryptogram generator configured to generate aunique cryptogram for emulation during a sequence of transactions orsingular transactions.

6. Tokens

Block S120 of the method S100 recites establishing a wireless connectionwith a mobile computing device; and Block S130 of the method S100recites, in response to establishing the wireless connection with themobile computing device, accessing a first token associated with thefirst cryptogram. Generally, in Blocks S120 and S130, the dynamictransaction card connects to the user's mobile computing device via awireless network (e.g., a local ad hoc network) to retrieve datapertinent to completing a transaction method stored on the dynamictransaction card. In particular, the dynamic transaction card canexecute Blocks S120 and S130 to download (and/or generate) a tokencorresponding to a particular transaction method—accessed previously bythe native application executing on the user's computing device, asdescribed above—which the dynamic transaction card then combines withthe cryptogram to generate a magnetic stripe sequence command for thistransaction method.

In one implementation and as described below, the dynamic transactioncard is paired to the user's computing device, such as over short-rangewireless communication protocol (as described in U.S. patent applicationSer. No. 13/904,939), and the native application executing on the mobilecomputing device stores an identifier (e.g., a unique wireless address)of the dynamic transaction card. When a new transaction method is loadedinto the native application,—such as by manual data entry, by opticalcharacter recognition of text in an image of a tangible plastictransaction card, or by accessing a related transaction account from athird party, as described above—the native application transmits arequest for a token for the transaction method to a token serviceprovider (i.e., an external token generator) or to a local tokengenerator stored locally on the dynamic transaction card or the mobilecomputing device. The token generator generates a token for thetransaction method and communicates the token to the mobile computingdevice; the mobile computing device then uploads the token with anidentifier of the corresponding transaction method to the dynamictransaction card. (The native application can also store a local copy ofthe token in memory on the mobile computing device and occasionallyupload the token to the dynamic transaction card based on requests toemulate the transaction method entered into the native application bythe user over time.)

Alternatively or additionally, the token can be a tokenized number,corresponding to a primary account number (hereinafter “PAN”), which, inturn, is associated with a transaction method. The token is preferablysent from the mobile computing device through an encrypted communicationmethod to the dynamic transaction card, but can alternatively beotherwise communicated. Subsequently, when a transaction is made withthe dynamic transaction card with the transaction method selected, a POSsystem receives (a form of) the token and a cryptogram at the dynamictransaction card specifically for the transaction; the token and thecryptogram are then routed from the POS system, through an acquirer, toa payment network.

In another variation, when a transaction is made with the dynamictransaction card, a local token generator—stored on the dynamictransaction card and synchronized with an authentication server—cangenerate a token and the dynamic transaction card can communicate thetoken, encrypted (e.g., “tokenized”) PAN, PAN, or other payment accountidentifier to the POS system through the magnetic stripe emulator,transmitter (e.g., antenna), or other communication means, and thenative application executing on the user's computing device cancommunicate the cryptogram to the POS system. The token and cryptogramare then routed from the POS to the payment network.

In the foregoing variation, the dynamic transaction card can store acounter of swipes of the dynamic transaction card through a POS systemin which the transaction method is set for emulation, and the dynamictransaction card can pass a value from this counter through the localtoken generator to generate the token. Each time the dynamic transactioncard detects a magnetic read head nearby and motion through a POSsystem, the dynamic transaction card can index the counter. Similarly,the authentication server can: maintain a remote counter for thistransaction method at the dynamic transaction card; index this remotecounter each time a cryptogram or other identifier of the transactionmethod at the dynamic transaction card is received from a POS; andpredict a token output by the dynamic transaction card during a nexttransaction in which the transaction method is set for emulation basedon the state of this second counter and a remote copy of the tokengenerator. When the dynamic transaction card connects wirelessly to themobile computing device during or after a transaction, the nativeapplication can interface with the dynamic transaction card and theauthentication server to reconcile the local counter stored on thedynamic transaction card and the remote counter.

Alternatively, the dynamic transaction card can synchronize an internaltimer with a global time (e.g., UTC time) when a wireless connection isestablished with the mobile computing device and then pass a value fromthe internal timer—at a time that a transaction at the dynamictransaction card is detected—into the token generator to generate atoken for the transaction. Upon receipt of transaction data from a POSsystem, the authentication server can predict the token output by thedynamic transaction card during this transaction based on the time(e.g., a five-minute time window) in which the transaction data wasreceived and a remote copy of the token generator. Similarly, thedynamic transaction card can append the magnetic stripe sequence commandwith a value (i.e., a timestamp) read from the internal timer at thetime of a detected transaction and output this time—in binary form—to aPOS system during the transaction. The authentication server can thenextract this timestamp from a bitstring received from the POS systemduring the transaction, pass this timestamp through a remote copy of thetoken generator, and then authenticate the transaction based onalignment between the token extracted from the bitstring and the tokencalculated remotely by the authentication server.

In another variation, when a transaction is made with the dynamictransaction card, the dynamic transaction card can communicate thetoken, tokenized PAN, PAN, or other payment account identifier to thePOS system through the magnetic stripe emulator, transmitter (e.g.,antenna), or other communication means, the POS system can route thetoken to the token generator, acquirer, and/or payment network, thetoken generator, acquirer, and/or payment network can generate and senda request to the user account associated with the dynamic transactioncard, and a native application executing on the user's computing devicecan send the cryptogram to the requesting entity for paymentverification. The payment network then cooperates with an issuer of thetransaction method and the token generator: to confirm the identity ofthe dynamic transaction card emulated in the transaction method byaccessing a registry of cryptograms associated with the dynamictransaction card; to decrypt the cryptogram by retrieving—from a domainname system affiliated with an issuer of the dynamic transactioncard—cryptographic protocols corresponding to the cryptogram (and/orcryptogram generator) programmed into the dynamic transaction card; todecrypt the token to identify the transaction method; to authenticatethe transaction with the transaction method based on the decryptedcryptogram and the decrypted token, and to pass back to the POS systemconfirmation of the transaction, such as in the form of a PAN productidentifier and a token assurance level.

Furthermore, in Block S130, the native application can request a groupof tokens for a (particular) transaction method and select—randomly orsequentially—a token, from the group of tokens, to transmit to thedynamic transaction card for a current or next transaction. For example,the dynamic transaction card can receive a group of seven tokens from anexternal token generator, wherein each token in the group of seventokens corresponds to a first transaction method (e.g., a first creditcard) enabled at the native application and dynamic transaction card. Inresponse to activation of the dynamic transaction card at a first time,such as by a user tapping, bending, or otherwise applying an input to asurface of the dynamic transaction card, the dynamic transaction cardcan: transmit a query for a token to the mobile computing device;receive a first token selected randomly from the group of seven tokensfrom the mobile computing device; output a first magnetic stripesequence command representing the first token and the cryptogram throughthe magnetic stripe emulator when subsequently swiped through a magneticstripe reader within a POS system; and then delete the first token andthe first magnetic stripe sequence command from local memory. At a latertime, in response to activation of the dynamic transaction card, thedynamic transaction card can: transmit a query for a token to the mobilecomputing device; receive a second token selected randomly from thegroup of seven tokens from the mobile computing device; output a secondmagnetic stripe sequence command representing the second token and thecryptogram through the magnetic stripe emulator when subsequently swipedthrough a magnetic stripe reader within another POS system; and thendelete the second token and the second magnetic stripe sequence commandfrom local memory.

However, the native application executing on the mobile computing devicecan retrieve a token for a new transaction method in any other way.

The dynamic transaction card can thus execute Block S130 to download atoken for a particular transaction method from the user's computingdevice. Similarly, the dynamic transaction card can further download amagnetic stripe sequence command for the transaction method from themobile computing device, such as described below and in U.S. patentapplication Ser. No. 13/904,939.

6.1 Visual Representation

Additionally, as shown in FIG. 7, the native application can receiveadditional information about the token and/or the transaction methodfrom the external token generator concurrently with the token. Forexample, the mobile computing device can download both a first token anda graphical representation of the transaction method associated with thefirst token, such as an icon or thumbnail image of a virtual creditcard, a credit card number, a financial account, or the financialinstitution. In response to receipt of the graphical representation ofthe transaction method and activation of the transaction method at thedynamic transaction card, the native application can render thegraphical representation of the transaction method in order tocommunicate to the user that this transaction method has been activatedand loaded onto the dynamic transaction card.

However, the native application executed by the mobile computing devicecan request and download any other additional information related to thetoken and/or the transaction method associated with tokens received bythe mobile computing device.

6.2 Storing Tokens

Furthermore, the dynamic transaction card can intransiently store atoken in memory (or a local token generator can generate a tokenlocally) and the dynamic transaction card emulate this token andcorresponding cryptogram during each subsequent use of the dynamictransaction card in which this transaction method is selected, asdescribed below. Alternatively, the native application can store thetoken in local memory on the mobile computing device and transmit this(single-use or multi-use) token to the dynamic transaction cardimmediately before a transaction with the dynamic transaction card forwhich a corresponding transaction method is selected.

In one implementation, the mobile computing device can store the tokenin local memory of the mobile computing device and selectively transmitthe token (or a form of the token) to the dynamic transaction card inresponse to a query from the dynamic transaction card. For example, thedynamic transaction card can detect an input (i.e., applied by a user)proximal a surface of the dynamic transaction card activating thedynamic transaction card for emulation of a magnetic stripe sequencecommand during a transaction. In response to activation of the dynamictransaction card, the dynamic transaction card can submit a query to themobile computing device for a token in preparation for a futuretransaction. Thus, the mobile computing device can transmit a storedtoken in response to the query.

In another implementation, the mobile computing device requests a tokenfrom the (local or external) token generator (e.g., on behalf of afinancial institution affiliated with the dynamic transaction card),receives an encrypted token from the token generator, and uploads theencrypted token to the dynamic transaction card. In this implementation,the dynamic transaction card can further decrypt the encrypted token andstore the decrypted token in memory of the dynamic transaction cardand/or the mobile computing device.

In the foregoing implementation, the dynamic transaction card can storethe token (or a decrypted form of the token) in local memory of thedynamic transaction card. In this implementation, the dynamictransaction card can confirm receipt of the token from the mobilecomputing device by transmitting a confirmation notice to the mobilecomputing device. In response to confirmation of receipt of the token,the mobile computing device can delete the token from local memory.

In another implementation, the native application executed by the mobilecomputing device can also request and store a new token for thetransaction method each time the transaction method is selected foremulation by the dynamic transaction card, each time the transactionmethod is selected for upload to the dynamic transaction card (e.g., inplace of an alternative transaction method loaded into the nativeapplication and/or into the user's dynamic payment account), and/or when(e.g., just before, just after) the token expires, as specified in atoken expiration date received with the token from the token generator.Thus, generally, the mobile computing device can receive and transmitsingle-use tokens to the dynamic transaction card for emulation during asingle transaction and, thus, delete the single-use tokens after use(i.e., emulation by the magnetic stripe emulator) or expiration of athreshold period of time (e.g., ten minutes) succeeding receipt of thesingle-use token.

For example, in response to activation of the dynamic transaction cardand default or active selection of a particular transaction method atthe dynamic transaction card, the dynamic transaction card can transmita query for a token for the particular transaction method to the mobilecomputing device over the wireless connection. Upon receipt of thisquery, the native application can request a single-use token from anexternal token generator and receive a first token from the externaltoken generator on behalf of a financial institution affiliated with thedynamic transaction card. The native application can then: return thefirst token to the dynamic transaction card; receive confirmation ofreceipt of the first token by the dynamic transaction card; and deletethe first token from local memory on the mobile computing device.Furthermore, in this example, in response to emulation of the firsttoken and the cryptogram by the magnetic stripe emulator during asubsequent transaction (e.g., in response to detecting a magnetic stripecard reader near the dynamic transaction card), the dynamic transactioncard can delete the first token from local memory on the dynamictransaction card. For additional security, the dynamic transaction cardcan delete the first token from local memory—regardless of whether themagnetic stripe emulator emulated the first token during atransaction—after expiration of a threshold duration of time (e.g., fiveminutes) following receipt of the first token from the mobile computingdevice.

However, the dynamic transaction card and the mobile computing devicecan access and store one or more single- or multi-use tokens in anotherway local to and/or remote from the dynamic transaction card.

7. Transaction Authentication

In one variation, the dynamic transaction card authenticates use of thedynamic transaction card for a subsequent transaction—once the dynamictransaction card enters a payment mode—by establishing wirelessconnectivity with the mobile computing device.

7.1 Wireless Connectivity

In one implementation and as described in U.S. patent application Ser.No. 13/904,939, the dynamic transaction card executes Block S120 byattempting—through the wireless communication module—to establish awireless connection with a computing device affiliated with the dynamictransaction card. For example, a unique wireless address correspondingto a mobile computing device (e.g., a smartphone) and previously linkedto the dynamic transaction card can be stored in memory on the dynamictransaction card. In this example, in response to transition from an offstate into a payment mode, the controller can trigger the wirelesscommunication module to attempt to pair wirelessly (e.g., overBluetooth) with a local computing device assigned the unique wirelessaddress. If the unique wireless address is found and a wirelessconnection with the associated computing device successfullyestablished, the controller can authorize use of the dynamic transactioncard in a subsequent transaction. The dynamic transaction card can thenexecute Block S120, as described below, to receive a selection for aparticular transaction method to emulate in a subsequent transaction inpreparation for the transaction.

In a similar implementation, the dynamic transaction card is operable ina sleep mode (or other low-power state) when not in use and occasionallytransitions into a test mode to check-in with the associated computingdevice to maintain authorization of use of the dynamic transaction card.For example, the dynamic transaction card can transition from the sleepmode into the test mode once per five-second interval (or at any otherfrequency or interval); once in the test mode, the wirelesscommunication module within the dynamic transaction card can broadcastan inquiry for the unique wireless address of the mobile computingdevice affiliated with the dynamic transaction card. In this example, ifa communication is received (wirelessly) from the mobile computingdevice in response to transmission of the inquiry (e.g., within 500milliseconds of transmitting the inquiry), the dynamic transaction cardcan preserve authorization of its use and transition back into the sleepmode. However, in this example, if a communication is not received fromthe mobile computing device within a threshold period of time (e.g., 500milliseconds) of transmitting the inquiry, the dynamic transaction cardcan transition into a locked state (or reattempt wireless communicationwith the mobile computing device by transmitting a second inquiry beforetransitioning into the locked state) in which emulation of a transactionmethod by the dynamic transaction card in a subsequent transaction isdisabled, such as until a passcode is entered into and authenticated atthe dynamic transaction card or until a wireless connection is againestablished with the mobile computing device, as shown in FIG. 8.Therefore, in this implementation, the dynamic transaction card canpreserve authorization of its use until a scheduled check-in with theaffiliated mobile computing device fails to yield a viable wirelessconnection with the mobile computing device. Alternatively, the dynamictransaction card can execute Block S120 to establish a (constant)wireless connection with the mobile computing device, to authorize itsuse in a subsequent transaction while the wireless connection persists,and to disable its use (e.g., disable emulation of a transaction method)when the wireless connection fails or is lost.

Thus, in the foregoing implementations, if the dynamic transaction cardsucceeds in establishing a wireless connection with a particular (e.g.,paired) mobile computing device, the controller can confirm that thedynamic transaction card is sufficiently near (e.g., within a thresholdauthentication range of) the mobile computing device, which may indicatethat an owner of the mobile computing device—who is also an owner of thedynamic transaction card—is within a suitable proximity to the dynamictransaction card. The controller can thus execute Block S120 toauthenticate use of the dynamic transaction card in a subsequenttransaction accordingly.

7.2 Wireless Connectivity Failure

However, in the foregoing implementation, if the wireless communicationmodule of the dynamic transaction card fails to establish a wirelessconnection with the mobile computing device, the controller of thedynamic transaction card can enter an inactive mode and/or delete thetoken and any other transaction account information associated with thetransaction method from the dynamic transaction card. Generally, thedynamic transaction card can execute Blocks of the method S100 to limitunauthorized use of the dynamic transaction card when separated from themobile computing device.

In one implementation, in response to disconnection or disruption of thewireless connection, the dynamic transaction card can delete the tokenfrom local memory. For example, due to separation of the dynamictransaction card from the mobile computing device beyond a thresholddistance or other aberrant function of the wireless module of thedynamic transaction card or the mobile computing device, the dynamictransaction card can delete the token and other transaction accountinformation (e.g., the graphical representation of the transactionmethod described above) from local memory of the dynamic transactioncard immediately succeeding disruption of the wireless connection.Alternatively, the controller can delete the token and/or othertransaction account information from local memory after a thresholdduration of time (e.g., three minutes) following disruption of thewireless connection. In this implementation, the mobile computing devicecan maintain the token in local memory of the mobile computing device,if present. Thus, the dynamic transaction card can be configured toprevent unauthorized use of the dynamic transaction card when separatedfrom the mobile computing device.

Alternatively, as described below, the dynamic transaction card canenter an inactive or low-power state in response to failure of thewireless connection between the dynamic transaction card and the mobilecomputing device. In this implementation, the controller can temporarilydisable the magnetic stripe emulator and ignore inputs to a surface ofthe dynamic transaction card while intermittently querying the wirelesscommunication at a sampling interval (e.g., every ten seconds for twominutes) to confirm absence of the wireless connection with the dynamictransaction card. In response to detecting reestablishment of thewireless connection between the dynamic transaction card and the mobilecomputing device, the controller can enter an active mode in which thecontroller receives and responds to inputs on the surface of the dynamictransaction card, such as by switching between preloaded transactionmethods.

However, the dynamic transaction card and the mobile computing devicecan restrict access and transmission of tokens and other transactionaccount information in any other way to limit unauthorized use of thedynamic transaction card when separated from the mobile computingdevice.

7.3 Passcode

Additionally or alternatively, as shown in FIG. 8, if the wirelesscommunication module of the dynamic transaction card fails to establisha wireless connection with the mobile computing device, the controllerof the dynamic transaction card can prompt the user to enter a passcodeas a backup authentication method in Block S122. Generally, the dynamictransaction card can request a passcode to override security measuresinhibiting function of the dynamic transaction card in the absence ofthe mobile computing device.

For example, the controller can trigger a visual indicator (e.g., an LEDlamp) within the dynamic transaction card to signal to the user failureto authenticate use of the dynamic transaction card (e.g., by flashingthe LED lamp) though wireless communication with the affiliated mobilecomputing device and to thus prompt the user to enter a passcode (e.g.,a three or four tap sequence applied to a surface of the dynamictransaction card) into the dynamic transaction card to manuallyauthenticate use of the dynamic transaction card. In thisimplementation, the controller can sample (e.g., poll) one or more inputregions on the dynamic transaction card to detect a sequence of inputsonto the dynamic transaction card, and the controller can authenticateuse of the dynamic transaction card if the sequence of inputs (e.g., asequence of taps to the surface of the dynamic transaction card) matchesa passcode stored on the dynamic transaction card, such as described inU.S. patent application Ser. No. 13/904,939.

Alternatively, the controller can execute Block S120 to transition intothe payment mode in response to receiving an authenticated passcodesequence onto a surface of the dynamic transaction card.

However, the dynamic transaction card can implement Block S120 in anyother way to authenticate use of the dynamic transaction card in asubsequent transaction, such as automatically based on proximity of thedynamic transaction card to a paired mobile computing device or based ona passcode entered manually into the dynamic transaction card, inresponse to entry of the dynamic transaction card into the payment mode.

7.4 Timing

Alternatively, the local token generator can generate a first tokenincluding a time stamp. Upon receipt of the token from the local tokengenerator, the dynamic transaction card can initiate a timer (e.g., 2minutes) during which the first token is active. Prior to expiration ofthe timer, the dynamic can generate a first magnetic stripe sequencecommand representing the first token and emulate the first magneticstripe sequence command in response to detecting a magnetic stripereader proximal the magnetic stripe emulator. Upon expiration of thetimer, the dynamic transaction card can delete the first token and thefirst magnetic stripe sequence command from local memory.

8. Modes & Inputs

In one implementation, the dynamic transaction card wakes from a sleepstate in response to an input (e.g., a tap) on a surface of the dynamictransaction card. In this implementation, the dynamic transaction cardcan trigger a piezoelectric circuit integrated in the dynamictransaction card to output a signal of sufficient voltage to trigger thecontroller within the dynamic transaction card to wake. The dynamictransaction card then executes Blocks of the method S100 to authorizeits use and retrieves from memory a selection for a default transactionmethod. The dynamic transaction card then pairs a token for the defaulttransaction method, received from a token generator, with a cryptogrampre-loaded onto the dynamic transaction card (or generates a cryptogramas described below) in preparation for use of the dynamic transactioncard. (Alternatively, the dynamic transaction card can pair the tokenand the cryptogram substantially in real-time as the token is downloadedto the dynamic transaction card and as the dynamic transaction card istapped on a wireless transaction reader or swept through a magneticstripe card reader.)

The dynamic transaction card can alternatively receive a selection for atransaction method through selection of a corresponding input region ona surface of the dynamic transaction card. Yet alternatively, thedynamic transaction card can receive a selection for a transactionmethod from the mobile computing device wirelessly connected to thedynamic transaction card, such as described in U.S. patent applicationSer. No. 14/542,092.

For example, the controller of the dynamic transaction card cantransition the dynamic transaction card from a low-power state (i.e.,inactive mode) into a payment mode in response to detecting a signal,output by a piezoelectric transducer arranged within the dynamictransaction card, that exceeds a preset threshold magnitude. In thisexample, the piezoelectric transducer can be configured to output asignal of magnitude corresponding to a degree of deflection of thedynamic transaction card out of a plane defined by a surface of thedynamic transaction card. Thus, in response to deflection of the dynamictransaction card before a preset deflect, such as by a user preparingfor a transaction, the dynamic transaction card can enter an activemode, wherein the controller is prepared to generate magnetic stripesequence commands from transaction account information and drive themagnetic stripe emulator according to a magnetic stripe sequencecommand.

Likewise, the controller of the dynamic transaction card can transitionthe dynamic transaction card from an active (e.g., payment) mode to aninactive (e.g., low-power) mode in response to detecting an inputproximal or coincident the dynamic transaction card.

However, the dynamic transaction card can execute Blocks of the methodS100 to intermittently transition between active and inactive modes inresponse to inputs to the dynamic transaction card.

9. Multiple Transaction Methods

Additionally, as shown in FIGS. 5 and 10, the dynamic transaction cardcan execute Blocks of the method S100 to receive, store, and selectivelyemulate multiple transaction methods through the (singular) dynamictransaction card. Generally, the dynamic transaction card can load a setof (varied and discrete) transaction methods to allocated memory of thedynamic transaction card and, in response to selection of a particulartransaction method, drive the magnetic stripe emulator to selectivelyemulate a magnetic stripe sequence command corresponding to theparticular transaction method while maintaining the other transactionmethods in local memory of the dynamic transaction card.

As described above, the dynamic transaction card can associateparticular transaction methods with input regions arranged on a surfaceof the dynamic transaction card such that upon selection of a particularinput region, the dynamic transaction card can drive the magnetic stripeemulator to emulate a particular transaction method. For example, thedynamic transaction card can store a first payment method in localmemory and associate the first payment method with a first input buttonon a surface of the dynamic transaction card. In response to detectingan input coincident the first input button (e.g., depression of ordetected touch coincident the first input button into the dynamictransaction card), the dynamic transaction card can select the firstpayment method, generate a first magnetic stripe sequence commandcorresponding to the first payment method, and drive the magnetic stripeemulator to emulate the first magnetic stripe sequence command.Similarly, in response to detection of a second input coincident (orproximal) the second input button, the dynamic transaction card canselect a second payment method and drive the magnetic stripe emulator toemulate a second magnetic stripe sequence command previously generatedby the dynamic transaction card for the second payment method.

Additionally, in response to detecting a second input coincident (orproximal) a second input region succeeding the first input, the dynamictransaction card can select a second transaction method to emulateduring an subsequent transaction at the dynamic transaction card andgenerate a second magnetic stripe sequence command according to thesecond transaction method in preparation for this upcoming transaction.

9.1 Single Encrypted+Multiple Unencrypted Transaction Methods

In one implementation shown in FIG. 5, the dynamic transaction card canload an encrypted transaction method and a set of unencryptedtransaction methods to local memory and selectively emulate theencrypted transaction and each transaction method in the set ofunencrypted transaction methods in response to selection. Generally, thedynamic transaction card can selectively download and emulate bothencrypted transaction methods processed through concurrent transmissionof cryptograms and tokens and unencrypted transaction methods processedthrough transmission of raw, unencrypted account information.

In particular, as described above, the dynamic transaction card canstore and emulate cryptograms and tokens of encrypted transactionmethods (e.g., virtual credit cards) issued from a financial institutionsponsoring production of the dynamic transaction card. To exploit thedynamic capability of the magnetic stripe emulator of the dynamictransaction card, the dynamic transaction card can also accept, store,and emulate additional transaction methods; however, the additionaltransaction methods can be emulated by the magnetic stripe emulatoraccording to magnetic stripe sequence commands corresponding to raw,unencrypted transaction information without tokens and cryptograms.

For example, in response to selection of the first encrypted transactionmethod (e.g., a virtual credit card), the dynamic transaction card can:generate or access a first magnetic stripe sequence commandcorresponding to (e.g., communicating) the cryptogram and the tokenrepresenting the first transaction method; and prepare the magneticstripe emulator to drive the magnetic stripe emulator according to thefirst magnetic stripe sequence command. Therefore, in response todetecting a magnetic stripe card reader proximal the dynamic transactioncard, the controller can drive the magnetic stripe emulator according tothe first magnetic stripe sequence command, thereby transmitting thecryptogram and the token of the first transaction method to the magneticstripe card reader at a POS system. As described above, the POS systemcan then transmit the cryptogram, the token, and transaction information(e.g., payment amount requested and location of the transaction) to apayment issuer affiliated with a financial institution hosting thetransaction method. Subsequently, in response to concurrent receipt ofthe cryptogram and the token, the payment issuer may issue payment tothe merchant, to authorize the transaction. However, in response toselection of a second transaction method in the set of unencryptedtransaction methods, the dynamic transaction card can: generate oraccess a second magnetic stripe sequence command corresponding tounencrypted transaction account information, such as credit cardnumbers, account holder name, account holder address, etc. in lieu of acryptogram and a token. In response to selection of a second transactionmethod, the controller of the dynamic transaction card can drive themagnetic stripe emulator according to the second magnetic stripesequence command, thereby transmitting the unencrypted transactionaccount information of the second transaction method to the magneticstripe card reader at a POS system.

In one variation of the foregoing implementation shown in FIG. 10, thedynamic transaction card can default to the first encrypted transactionmethod in the absence of an explicit selection of the second(unencrypted) transaction method in Block S114. Generally, in thisvariation, the dynamic transaction card can be configured to maintainhigh encryption and security of transaction methods emulated by thedynamic transaction card by default unless an alternate (unencrypted)transaction method is purposefully selected for emulation. For example,the dynamic transaction card can drive the magnetic stripe emulatoraccording to the first magnetic stripe sequence command, correspondingto the cryptogram and the token associated with the first encryptedtransaction method, by default (in lieu of selection of a differenttransaction method). However, in response to selection of an inputregion of the dynamic transaction card assigned to the secondtransaction method, the dynamic transaction card can drive the magneticstripe emulator according to the second magnetic stripe sequencecommand, corresponding to the unencrypted account information of thesecond transaction method.

In the foregoing variation shown in FIG. 11, the second (unencrypted)transaction method can correspond to lower security transaction methods,such as lower security credit cards and debit cards (e.g., affiliatedwith a financial institution other than the financial institutionsponsoring manufacture of the dynamic transaction card), gift cards,loyalty program cards, etc. For example, the second (unencrypted)transaction method can correspond to a loyalty account associated with aloyalty rewards program. In this implementation, the native applicationcan receive loyalty account information and transmit the loyalty accountinformation to the dynamic transaction card for local storage. Thedynamic transaction card can thus generate a second magnetic stripesequence command corresponding to the unencrypted loyalty accountinformation. Alternatively, the dynamic transaction card can downloadthe second magnetic stripe sequence command for the second (unencrypted)transaction method directly from the mobile computing device or anexternal (remote) server. In this example, in response to selection ofthe second transaction method, such as by depression of an input regionassigned to the second transaction method, and in response to detectinga magnetic stripe card reader proximal the dynamic transaction card, thecontroller of the dynamic transaction card can drive the magnetic stripeemulator according to the second magnetic stripe sequence command.

Additionally or alternatively, the dynamic transaction card can selectthe second transaction method (and/or the first transaction method)based on relevance of the second transaction method at a currentlocation of the dynamic transaction card. Generally, in thisimplementation, the dynamic transaction card can be configured todefault to emulate a first (encrypted) transaction method unless asecond transaction method is more relevant or financially advantageousto the user under current conditions.

In particular, the user may belong to a loyalty rewards program for aparticular merchant or hold a merchant-sponsored credit card accountaffiliated with the particular merchant. During transactions at theparticular merchant, in response to employing the loyalty rewardsprogram or the merchant-sponsored credit card rather than analternative, unaffiliated transaction method, the merchant may rewardthe user with discounts, rewards points, loyalty gifts, etc. As shown inFIGS. 11 and 12, to incentivize transactions employingmerchant-affiliated transaction methods during transactions at theparticular merchant, the dynamic transaction card can, thus,automatically select relevant merchant-affiliated transactions methods,instead of the default, encrypted transaction method, based on a currentlocation of the dynamic transaction card. For example, the dynamictransaction card can request and receive the current location from themobile computing device. Based on the current location, the dynamictransaction card can select a transaction method corresponding to aloyalty account relevant (i.e., applicable) to the current location and,thus, drive the magnetic stripe emulator according to a second magneticstripe sequence command corresponding to the loyalty account.

9.2 Multiple Encrypted Transaction Methods

In another implementation, the dynamic transaction card can be preloadedwith multiple static cryptograms. Generally, in this implementation, thedynamic transaction card can store and emulate multiple encryptedtransaction methods by pairing encrypted tokens representing transactionmethods with (encrypted) cryptograms representing a unique addresswithin the dynamic transaction card.

In particular, in this implementation, an external cryptogram generator,such as a dynamic transaction card issuer, may preload the dynamictransaction card with a group of cryptograms and supply a log (orregistry) of the group of cryptograms to a financial institutionaffiliated with the dynamic transaction card issuer. Upon receipt of thedynamic transaction card, the user may pair the dynamic transaction cardwith the mobile computing device, thereby informing the financialinstitution that the (particular) dynamic transaction card including the(particular) group of cryptograms corresponds to the (particular) useraffiliated with the (particular) mobile computing device. Thus, thenative application of the mobile computing device can load a set oftokens representing a set of transaction methods affiliated with the(particular) user. The dynamic transaction card can download—inreal-time, sequentially, or asynchronously—the set of tokens from themobile computing device and store the tokens in local memory.Additionally, the dynamic transaction card can pair each token in theset of tokens with a cryptogram in the group of cryptograms. Thus, thedynamic transaction card can generate a set of magnetic stripe sequencecommands representing each token and cryptogram pair and, thus,representing each encrypted transaction method. In response to detectinga magnetic stripe card reader proximal the dynamic transaction card andin response to selection of a particular transaction method, the dynamictransaction card can drive the magnetic stripe emulator to output aparticular magnetic stripe sequence command corresponding to thecryptogram and token pair representing the particular transactionmethod.

9.3 Dynamic Cryptogram Generator

Based on a selection for the particular transaction method from the setof transaction methods, generating a cryptogram corresponding to theparticular transaction method. Generally, the dynamic transaction cardcan, in response to an input on a surface of the dynamic transactioncard, generate a one-time-use cryptogram (or authorization code, etc.)for transmission in an upcoming transaction.

Once selection of a transaction method is made or received at thedynamic transaction card (and/or one a transaction with the transactionmethod is initiated), the dynamic transaction card can trigger thecryptogram generator to output a one-time-use cryptogram for thetransaction. The cryptogram generator can be generic to all tokenizedtransaction methods emulated at the dynamic transaction card.Alternatively, the dynamic transaction card can host multiple cryptogramgenerators, such as one substantially unique cryptogram generator pertransaction method loaded onto the dynamic transaction card, and thedynamic transaction card can thus trigger a particular cryptogramgenerator—relevant to a particular transaction method selected for anupcoming transaction—to output a cryptogram for the upcomingtransaction. For example, the dynamic transaction card can download atransaction package for a transaction method from the dynamictransaction card, the transaction package including both a static tokenand a corresponding cryptogram generator specific to the transactionmethod.

Therefore, in one implementation, the dynamic transaction card ispre-loaded with multiple cryptogram generators (e.g., “secret keys” forgenerating different varieties of cryptograms). In this implementation,the various cryptogram generators can execute correspondingcryptographic schemes, and the dynamic transaction card can thus emulatevarious transaction methods through various tokens schemes and variouscorresponding cryptographic schemes hosted by various token generators.

In another implementation, the dynamic transaction card is notpre-loaded with a cryptogram generator. Rather, once the user takesreceipt of the dynamic transaction card and the dynamic transaction cardis linked to the user's computing device, the native applicationexecuting on the user's computing device retrieves an encryptedcryptogram generator (e.g., a cryptogram scheme) from a service providerand uploads the encrypted cryptogram generator to the dynamictransaction card. The dynamic transaction card then decrypts theencrypted cryptogram generator during a transaction with the dynamictransaction card. In this implementation, the dynamic transaction cardcan thus receive and execute new cryptographic “profiles” over time(e.g., after the dynamic transaction card is issued into the field),thereby enabling greater token service support. Furthermore, in thisimplementation, the dynamic transaction card can thus be shipped to auser devoid of secure content, and the native application—executing onthe user's computing device—can upload secure content (e.g.,cryptographic protocols, tokens, etc.) to the dynamic transaction cardonce the dynamic transaction card is linked to and wireless connected tothe user's computing device.

However, the dynamic transaction card can generate a cryptogram for atransaction method selected for an upcoming transaction in any otherway.

10. Magnetic Stripe Sequence Command

As shown in FIG. 9, Block S140 of the method S100 recites generating afirst magnetic stripe sequence command representing the first cryptogramand the first token. Generally, the dynamic transaction card can executeBlock S140 of the method S100 to transform the cryptogram and the tokenassociated with a particular transaction method into a magnetic stripesequence command configured to drive the magnetic stripe emulator toemulate a magnetic stripe sequence corresponding to and transmitting thecryptogram and the token to a POS.

As described above, the dynamic transaction card (or an externalmagnetic stripe sequence command generator) can generate a magneticstripe sequence command corresponding to account information and/or atoken and a cryptogram representing account information of a particulartransaction method.

In one example implementation, the dynamic transaction card can downloadand store a first bitstring representing a cryptogram and a secondbitstring representing a token. For example, the first bitstring caninclude thirty-two bits and the second bitstring can includesixteen-bits representing an encrypted form of a credit card number.Thus, in this example implementation, the dynamic transaction card cangenerate a comprehensive bitstring representing both the token and thecryptogram by compiling the first and second bitstrings in series, inparallel, or in any other order. From the comprehensive bitstring, thecontroller can generate a magnetic stripe sequence command directlycorresponding to the comprehensive bitstring.

Furthermore, the controller can prepend the comprehensive bitstring witha swipe initiation sequence and append the comprehensive bitstring witha swipe termination sequence. Thus, the dynamic transaction card cangenerate a magnetic stripe sequence command including an initiationsequence indicating to a magnetic stripe card reader where, during aswipe, the magnetic stripe card reader can read important transactioninformation relayed by the magnetic stripe sequence emulated by themagnetic stripe emulator. Likewise, the dynamic transaction card cangenerate the magnetic stripe sequence command to include a terminationsequence indicating where the important transaction informationterminates.

However, the dynamic transaction card can generate and/or access themagnetic stripe sequence command in any other suitable way.

10.1 Emulation: Wireless Transaction

At the radio-frequency wireless transmitter, broadcasting the cryptogramand a form of a token corresponding to the particular transaction methodin response to detection of a wireless transaction reader proximal thedynamic transaction card.

Generally, the dynamic transaction card can broadcast a variety of datasufficient to complete a transaction with the selected transactionmethod—such as the corresponding token, token expiry date, cryptogram,etc.—to a wireless transaction reader detected near the dynamictransaction card, as shown in FIG. 2.

In one implementation, the dynamic transaction card assembles atransaction packet including a token, a token expiry date, a cryptogram,etc. and other chip data elements corresponding to a selectedtransaction method in response to activation of the dynamic transactioncard and/or selection of the transaction method for an upcomingtransaction, and the radio-frequency wireless transmitter (or otherwireless communication module) within the dynamic transaction cardbroadcasts the transaction packet over short-range wirelesscommunication protocol (e.g., NFC) in response to receipt of atransaction request from an adjacent wireless transaction reader withina merchant's POS system terminal.

10.2 Emulation: Magnetic Stripe

Blocks S140 and S150 of the method S100 recite: generating a firstmagnetic stripe sequence command representing the first cryptogram andthe first token in Block S140; and in response to detecting a magneticstripe card reader proximal a magnetic stripe emulator integrated intothe dynamic transaction card at a third time succeeding the second time,driving the magnetic stripe emulator according to the first magneticstripe sequence command in S150. Generally, the dynamic transaction cardcan execute Blocks S140 and S140 to transmit transaction data for theselected transaction method—via the magnetic stripe emulator—to amagnetic stripe card reader within a merchant's POS system terminal, asshown in FIG. 2.

In particular, the dynamic transaction card can emulate the selectedtransaction method by selectively transmitting the corresponding tokenand cryptogram over radio-frequency wireless communication or via themagnetic stripe emulator based on detected proximity of a wirelesstransaction reader or detected proximity of a magnetic stripe cardreader, respectively, to the dynamic transaction card. For example, thedynamic transaction card can sample one or more integrated magneticstripe card reader sensors within the dynamic transaction card to detectan adjacent magnetic stripe card reader, can drive the magnetic stripeemulator according to a magnetic stripe sequence command correspondingto the selected transaction method in Block S140 if a magnetic stripecard reader is detected. (The dynamic transaction card can alsobroadcast the token and cryptogram for the selected transaction method(and disable the magnetic stripe emulator) if a transaction request isreceived from a wireless transaction reader, as described above).

In one implementation, the dynamic transaction card emulates a staticmagnetic stripe sequence command output by a static transaction method(e.g., a static credit card, a static debit card) by driving one or moretracks within the magnetic stripe emulator according to a correspondingmagnetic stripe sequence command. For example, the mobile computingdevice can interface with a magnetic stripe card reader to read anoutput of the transaction method (e.g., a credit card, a debit card) andthen generate a magnetic stripe sequence command based on magneticfields reader from the transaction method; the dynamic transaction cardthen downloads the magnetic stripe sequence command and drives one ormore tracks within the magnetic stripe emulator accordingly when thedynamic transaction card is swept through a magnetic stripe card reader.In this implementation, in Blocks S140 and S150, the dynamic transactioncard can drive a first track (e.g., Track 1) of the magnetic stripeemulator according to the magnetic stripe sequence command generated forthe token and also drive a second track (e.g., Track 2) within themagnetic stripe emulator according to a magnetic stripe sequence commandgenerated for the cryptogram substantially simultaneously as the dynamictransaction card is swept through a magnetic stripe card reader. In thisimplementation, the magnetic stripe card reader (in a merchant's POS)can thus pass a form of the token and the cryptogram from the dynamictransaction card to an acquirer (i.e., a merchant hosting a POS) and onto a payment network for authentication. The payment network can thencooperate with an issuer of the transaction method and the token serviceprovide authenticate the transaction based on the magnetic stripesequence command representing the token and the cryptogram, as shown inFIG. 2.

In another implementation, the dynamic transaction card generates aone-time-user magnetic stripe sequence command based on the token andthe cryptogram generated for the transaction. For example, the dynamictransaction card can execute Block S140 to generate a Track 1 (Format B)magnetic stripe sequence command including the token, the cryptogram, anexpiration date of the token, and a service code. In this example, thedynamic transaction card can set the token in place of a primary accountnumber (PAN) in a Format B magnetic stripe sequence command and can setthe cryptogram in place of a PIN Verification Value (PVV) in the FormatB magnetic stripe sequence command to generate a command for Format Bmagnetic stripe sequence command including: a start sentinel, a formatcode, a PAN (now the token), a first field separator, a name field(blank), a second field separator, an expiration date (the expirationdate of the token), a service code (e.g., including a pointer to thetoken generator), a PVV (now the cryptogram), and an end sentinel. Thedynamic transaction card can thus output the one-time-use Format Bmagnetic stripe sequence command—via the magnetic stripe emulator—inBlock S150 when the dynamic transaction card is swept through a magneticstripe card reader.

However, the dynamic transaction card can emulate a selected transactionmethod through the magnetic stripe emulator in Blocks S140 and S150,respectively, in any other suitable way.

As described below, the dynamic transaction card can also incorporateone or more chip pin pads, and the dynamic transaction card canadditionally or alternatively similarly emulate a selected transactionmethod via all or a subset of the chip pin pads (e.g., based on a typeor contact-based transaction method being emulated), as described above.In this variation, the dynamic transaction card can thus emulate variousdifference types of transaction chips by transmitted tokenizedtransaction data through one or more chip pin pads integrated into thedynamic transaction card.

11. Post Transaction

In one implementation, immediately following emulation of the magneticstripe sequence command by the magnetic stripe emulator (and/or passageof the magnetic stripe emulator through a magnetic stripe card reader),the dynamic transaction card can initiate a timer over which thecontroller is active and prepared to drive the magnetic stripe emulatoraccording to the magnetic stripe sequence command in response todetecting proximity of a magnetic stripe card reader to the dynamictransaction card. Generally, upon expiration of the timer following aninstance of emulation of the magnetic stripe sequence command by themagnetic stripe emulator, the dynamic transaction card can enter aninactive (or “sleep”) mode in which the magnetic stripe emulator isinoperable until the dynamic transaction card is explicitly activated,such as by an input to the surface of the dynamic transaction card.Furthermore, while the timer is active, the controller can continue todrive the magnetic stripe emulator according to the magnetic stripesequence command. Thus, in this implementation, to secure the card afteruse, the dynamic transaction card can configure the timer to limit aduration of time (and, thus, a number of swipes) after activation andemulation that the dynamic transaction card can emulate a transactionmethod.

In this implementation, while the timer is active, the controller canintermittently look for the magnetic stripe card reader proximal themagnetic stripe emulator at a sampling interval (e.g., every 0.1 ms). Inresponse to detection of the magnetic stripe card reader proximal themagnetic stripe card reader prior to expiration of the timer, thecontroller can continue to drive the magnetic stripe emulator accordingto the magnetic stripe sequence command. However, after expiration ofthe time, the dynamic transaction card can disable the magnetic stripeemulator.

11.1 Delete Token

Furthermore, in response to confirmation of emulation of a particularmagnetic stripe sequence command corresponding to a transaction methodrepresented by a token and a cryptogram, the dynamic transaction cardcan delete the token from local memory at the native application and/orat the dynamic transaction card while maintaining the cryptogram.Furthermore, the dynamic transaction card can delete the magnetic stripesequence command from local memory at the dynamic transaction card.Generally, in this implementation, the dynamic transaction card can beconfigured to limit local storage of sensitive transaction accountinformation by deleting the sensitive transaction account informationfollowing use.

Alternatively, following emulation of the magnetic stripe sequencecommand, the dynamic transaction card can, as described above, initiatea timer. While the timer is active, the dynamic transaction card canmaintain the token and/or the magnetic stripe sequence command in localmemory of the dynamic transaction card. After expiration of the timer,the dynamic transaction card can purge the token and the magnetic stripesequence command from local memory.

11.2 Output Secondary Transaction Method

As described above and shown in FIG. 6, the dynamic transaction card canemulate multiple transaction methods—encrypted and unencrypted. In oneimplementation, the dynamic transaction card can detect multiplesuccessive swipes of the dynamic transaction card through a magneticstripe card reader within a threshold period of time; and switchtransaction methods and sequentially reduce encryption strength witheach successive swipe. Generally, in this implementation, the dynamictransaction card can be configured to switch transaction methods inresponse to triggers indicating failure (i.e., non-acceptance) of aparticular transaction method at a POS system.

In particular, at a first time, the dynamic transaction card can detecta magnetic stripe card reader proximal the magnetic stripe emulatorduring a first swipe through the magnetic stripe card reader integratedinto a POS system and drive the magnetic stripe emulator according to afirst magnetic stripe sequence command corresponding a first cryptogramand a first token representing a (default) first transaction method.However, at a second time succeeding the first time and within a presetduration of the first time (e.g., 3 seconds), the detect can detectinitiation of second swipe of the dynamic transaction card through themagnetic stripe card reader. In response to initiation of the secondswipe, the dynamic transaction card can flag the first swipe as anineffective swipe (e.g., due to a failure of the magnetic stripe cardreader). Thus, the dynamic transaction card can drive the magneticstripe emulator according to the (same) first magnetic stripe sequencecommand during the second swipe. If the dynamic transaction card detectsno more swipes following the second swipe for a threshold duration oftime (e.g., thirty seconds), the dynamic transaction card can mark thesecond swipe successful and disregard the first swipe as an ineffectivemiscommunication between the dynamic transaction card and the magneticstripe card reader. However, if, at a third time, the dynamictransaction card detects initiation of a third swipe following thesecond swipe within the threshold duration of time, the dynamictransaction card can drive the magnetic stripe emulator according to asecond magnetic stripe sequence command corresponding to unencryptedaccount information of a second transaction method. Furthermore, basedon success third swipe (i.e., no additional swipe succeeding the thirdswipe for a threshold duration), the dynamic transaction card candetermine that the POS system does not accept encrypted transactionswithout direct two-way communication between the POS system and thedynamic transaction card.

Additionally, in another implementation, the dynamic transaction cardcan record (POS system) locations where particular encryption protocolsare successful and unsuccessful. Generally, the dynamic transaction cardcan cooperate with financial institutions to map encryption protocols ofpoints of sales at various merchants in order to predict a successfulencryption scheme for a transaction at a particular POS system prior tothe transaction and, therefore, avoid multiple swipes.

In particular, the dynamic transaction card can in response to successof the first transaction described above, the native applicationexecuted by the mobile computing device can record a first location ofthe first transaction and associate the first location with acceptanceof encrypted tokenized transactions (i.e., employing cryptograms andtokens). (The mobile computing device can access the first location ofthe mobile computing device through a GPS-module or otherlocation-sensing module integrated into the mobile computing device). Inresponse to failure of the first transaction and success of the secondtransaction, dynamic transaction card can similarly associate the firstlocation of the first transaction with encrypted tokenized transactions.However, in response to failure of the second transaction and success ofthe third transaction wherein the magnetic stripe emulator emulatesunencrypted transaction information, the native application can record athird location of the third transaction and associate the third locationwith acceptance of unencrypted transaction.

From the first and third locations, the native application, financialinstitutions, and other users of the other dynamic transaction cards cancooperate to define a (crowd-sourced map) identifying securitypreferences and encryption protocols of points of sale. Based on themap, the dynamic transaction card can preemptively select a transactionmethod for a particular location prior to a transaction, the transactionmethod including encryption protocols corresponding to known encryptionprotocols at the particular location. Thus, the dynamic transaction cardcan avoid sequential testing of various encryption protocols at everyPOS system for every transaction.

However, the dynamic transaction card and the mobile computing devicecan cooperate in any other suitable way to adapt to various encryptionprotocols of points of sale prior to transactions at said points of salewhile maintaining the highest encryption level acceptable at each POSsystem during each transaction with the dynamic transaction card.

12. Replacement Payment Methods

As described above and shown in FIG. 7, Blocks of the method S100 can beimplemented to facilitate replacement and renewal of transaction (orpayment) methods by receiving new virtual transaction methods from afinancial institution wirelessly over the wireless connection.Generally, Blocks of the method S100 can be implemented to securelyreplace a compromised virtual transaction method with a new virtualtransaction method without requiring the financial institution to issuean entirely new physical card.

In particular, the financial institution may issue a (new) secondpayment method. In this implementation, the dynamic transaction card canstore in local memory the first payment method represented by a firsttoken and a first cryptogram. Thus, the native application can download,from the local (or external) token generator, a second tokenrepresenting a second payment method associated with the financialaccount. Additionally, the native application and the dynamictransaction card can delete a first token representing the first paymentmethod from local memory. Thus, the dynamic transaction card candownload the second token to the dynamic transaction card via thewireless connection.

In one implementation, the dynamic transaction card can pair the secondtoken with the first cryptogram, thereby maintaining a cryptogram andreplacing a token to emulate a replacement payment method. In anotherimplementation, the dynamic transaction card can pair the second tokenwith a second cryptogram, thereby replacing both a cryptogram a token toemulate a replacement payment method for enhanced security in the eventthe first payment method was compromised.

The native application can download replacement transaction (or payment)methods in response to receipt of fraud detection related to the firstpayment method (e.g., a financial account hosted by the financialinstitution) from the financial institution. For example, the financialinstitution may detect aberrant activity of the first payment method ata location remote from the dynamic transaction card or the financialinstitution may detect unusual spending (e.g., excessively high) withfirst payment method. In response to detecting aberrant or unusualactivity, the dynamic transaction card can issue a new payment method tothe native application wirelessly. Furthermore, the financialinstitution may issue new payment methods periodically, such as everysix months, for enhanced security.

Additionally or alternatively, the mobile computing device can receiveand store PAN and other account information of a replacement transactionmethod in local memory of the mobile computing device prior toactivation of the replacement transaction method at the financialinstitution. In response to establishing a wireless connection (i.e.,“pairing”) between the mobile computing device and the dynamictransaction card, the mobile computing device can transmit thereplacement transaction method to the dynamic transaction card, therebyactivating the replacement transaction method with the financialinstitution. Upon receipt of the replacement transaction method andactivation of the replacement transaction method with the financialinstitution, the local token generator can generate a token representingthe PAN of the replacement transaction method.

However, the native application and the financial institution cancooperate in another suitable way to issue replacement transactionmethods in response to any other trigger. Additionally, the dynamictransaction card can update transaction methods stored in local memoryto correspond with replacement transaction methods in any other suitableway.

13. EMV

In one variation of the method S100, the dynamic transaction card canalso include an integrated EMV-chip (or other integrated chip-cardcircuit) configured to output a cryptogram and a token for a transactionmethod in response to insertion of the EMV-chip into a chip-card readerfor a transaction.

In one example implementation, the dynamic transaction card can locallystore a single encrypted transaction method in local memory. Thus, inresponse to detecting the EMV-chip proximal a chip-card reader, theEMV-chip can output a signal (i.e., emulate) corresponding to thecryptogram and the token representing the single encrypted transactionmethod.

Likewise, the dynamic transaction card can locally store a set ofencrypted transaction methods, each encrypted transaction methods in theset of encrypted transaction methods represented by a unique token and aunique cryptogram. In response to detecting the EMV-chip proximal achip-card reader and in response to selection of a particular encryptedtransaction method from the set of encrypted transaction methods, theEMV-chip can output a signal corresponding to the unique token and theunique cryptogram.

15. Card-Not-Present Transaction

In one variation, the dynamic transaction card cooperates with thenative application executing on the user's computing device to completean online transaction through the mobile computing device. In oneexample, the user taps the dynamic transaction card three time totrigger the dynamic transaction card to enter an “online transactionmode,” and the dynamic transaction card authenticates its use, asdescribed above. In this example, the dynamic transaction card thenexecutes generates a new cryptogram for an upcoming online transactionwith a selected transaction method, packages the new cryptogram and atoken corresponding to the selected transaction method, and transmitsthe cryptogram and token back to the mobile computing device; the nativeapplication then disseminates the cryptogram and token: to an othernative application to complete a transaction within the other nativeapplication; into a webpage or other interface within a web browserexecuting on the mobile computing device; or directly to an acquirerwith a tag identifying the online transaction initiated through anothernative application or web browser executing on the user's computingdevice. As in this example, the dynamic transaction card can thusauthenticate a transaction with a transaction method hosted by thedynamic transaction card, such as by requiring a valid fingerprint scanat the dynamic transaction card and/or by requiring a wirelessconnection between the dynamic transaction card and an associatedcomputing device (e.g., a smartphone), and the dynamic transaction cardcan selectively supply transaction data for a selected transactionmethod accordingly to enable secure “card-not-present” (e.g., online,remote) transaction.

The systems and methods described herein can be embodied and/orimplemented at least in part as a machine configured to receive acomputer-readable medium storing computer-readable instructions. Theinstructions can be executed by computer-executable componentsintegrated with the application, applet, host, server, network, website,communication service, communication interface,hardware/firmware/software elements of a user computer or mobile device,wristband, smartphone, or any suitable combination thereof. Othersystems and methods of the embodiment can be embodied and/or implementedat least in part as a machine configured to receive a computer-readablemedium storing computer-readable instructions. The instructions can beexecuted by computer-executable components integrated bycomputer-executable components integrated with apparatuses and networksof the type described above. The computer-readable medium can be storedon any suitable computer readable media such as RAMs, ROMs, flashmemory, EEPROMs, optical devices (CD or DVD), hard drives, floppydrives, or any suitable device. The computer-executable component can bea controller but any suitable dedicated hardware device can(alternatively or additionally) execute the instructions.

As a person skilled in the art will recognize from the previous detaileddescription and from the figures and claims, modifications and changescan be made to the embodiments of the invention without departing fromthe scope of this invention as defined in the following claims.

We claim:
 1. A method comprising: at a dynamic transaction card: at afirst time, storing a group of cryptograms generated by a localcryptogram generator stored on the dynamic transaction card, the groupof cryptograms comprising the first cryptogram and a second cryptogramdistinct from the first cryptogram; at a second time, establishing awireless connection with a mobile computing device; in response toestablishing the wireless connection with the mobile computing device,at a local token generator stored on the dynamic transaction card,generating a first token associated with the first cryptogram;generating a first magnetic stripe sequence command representing thefirst cryptogram and the first token by fusing the first cryptogram andthe first token representing a first payment method; in response todetecting a magnetic stripe card reader proximal a magnetic stripeemulator integrated into the dynamic transaction card at a third timesucceeding the second time, driving the magnetic stripe emulatoraccording to the first magnetic stripe sequence command; at the localtoken generator, generating a second token associated with the secondcryptogram; generating a second magnetic stripe sequence commandrepresenting the second cryptogram and the second token by fusing thesecond cryptogram and the second token representing a second paymentmethod; at a fourth time succeeding the third time, receiving aselection for the second payment method; and at approximately the fourthtime, in response to detecting a second magnetic stripe card readerproximal the magnetic stripe emulator, driving the magnetic stripeemulator according to the second magnetic stripe sequence command. 2.The method of claim 1, wherein storing the group of cryptogramscomprises: storing the first cryptogram comprising a first single-usecryptogram; and storing the second cryptogram comprising a secondsingle-use cryptogram.
 3. The method of claim 1, further comprising, atthe dynamic transaction card, in response to passage of a thresholdduration of time following the third time, deleting the first token fromthe dynamic transaction card.
 4. The method of claim 1: wherein drivingthe magnetic stripe emulator comprises driving the magnetic stripeemulator according to the first magnetic stripe sequence command whilethe wireless connection is current; and further comprising, in responseto failure of the wireless connection, deleting the first token from thedynamic transaction card.
 5. The method of claim 1: further comprising,in response to failure of the wireless connection: entering an inactivemode, the magnetic stripe emulator deactivated in the inactive mode; inresponse to receipt of a passcode entered on a surface of the dynamictransaction card, entering an active mode; and wherein driving themagnetic stripe emulator according to the first magnetic stripe sequencecommand comprises, in the active mode, in response to detecting amagnetic stripe card reader proximal the magnetic stripe emulator,driving the magnetic stripe emulator according to the first magneticstripe sequence command.
 6. The method of claim 1: further comprising:associating the first payment method with a first input region on asurface of the dynamic transaction card; and associating the secondpayment method with a second input region on the surface of the dynamictransaction card; wherein driving the magnetic stripe emulator accordingto the first magnetic stripe sequence command comprises driving themagnetic stripe emulator according to the first magnetic stripe sequencecommand by default; and wherein driving the magnetic stripe emulatoraccording to the second magnetic stripe sequence command comprisesdriving the magnetic stripe emulator according to the second magneticstripe sequence command in response to selection of the second inputregion.
 7. The method of claim 1, further comprising: at a nativeapplication executing on the mobile computing device: receiving aloyalty account associated with a loyalty program; at the dynamictransaction card: downloading a second magnetic stripe sequence commandrepresenting the loyalty account from the mobile computing device viathe wireless connection; storing the second magnetic stripe sequencecommand in local memory of the dynamic transaction card; at a fourthtime succeeding the third time, in response to receiving a selection ofthe loyalty account and detecting a second magnetic stripe card readerproximal the magnetic stripe emulator, driving the magnetic stripeemulator according to the second magnetic stripe sequence command. 8.The method of claim 7: further comprising, in response to detecting thewireless connection, receiving a current location of the mobilecomputing device; and wherein driving the magnetic stripe emulatoraccording to the second magnetic stripe sequence command comprises:selecting the loyalty account based on relevance of the loyal account atthe current location; and in response to selection of the loyaltyaccount, driving the magnetic stripe emulator according to the secondmagnetic stripe sequence command.
 9. The method of claim 1: whereinstoring the group of cryptograms comprises storing the first cryptogramcomprising a thirty-two-bit bitstring; wherein generating the firsttoken comprises generating the first token comprising a sixteen-bitbitstring at the local token generator; and wherein fusing the firstcryptogram and the first token to form a first payment method comprisescompiling the thirty-two-bit bitstring and the sixteen-bit bitstringinto the first magnetic stripe sequence command.
 10. The method of claim1: wherein driving the magnetic stripe emulator according to the firstmagnetic stripe sequence command comprises, at approximately the thirdtime, driving the magnetic stripe emulator according to the firstmagnetic stripe sequence command in a first transaction; and furthercomprising: at a native application executing on the mobile computingdevice: downloading a second payment method; at the dynamic transactioncard: downloading a second magnetic stripe sequence command representingthe second payment method from the mobile computing device via thewireless connection; storing the second magnetic stripe sequence commandin local memory of the dynamic transaction card; and in response tofailure of the first transaction at a POS system and in response todetection of the magnetic stripe card reader proximal the dynamictransaction card within a threshold duration of the third time, drivingthe magnetic stripe emulator according to the second magnetic stripesequence command in a second transaction.
 11. The method of claim 1,further comprising, in response to detecting a chip-card reader at anintegrated chip-card circuit of the dynamic transaction card, outputtingthe first token and the first cryptogram via the integrated chip-cardcircuit.
 12. A method comprising: at a native application executing on amobile computing device: receiving a first token from an external tokengenerator generated on behalf of a financial institution; and storingthe first token in local memory on the mobile computing device, thefirst token representing a first payment method associated with afinancial account; at a dynamic transaction card: at a first time,storing a group of cryptograms comprising the first cryptogram and asecond cryptogram; at a second time, establishing a wireless connectionwith the mobile computing device; detecting activation of the dynamictransaction card at approximately the second time; in response toactivation of the dynamic transaction card, transmitting a query for atoken to the mobile computing device over the wireless connection;downloading the first token from the mobile computing device; generatinga first magnetic stripe sequence command representing the firstcryptogram and the first token; and in response to detecting a magneticstripe card reader proximal a magnetic stripe emulator integrated intothe dynamic transaction card at a third time succeeding the second time,driving the magnetic stripe emulator according to the first magneticstripe sequence command; at the native application, in response toreceipt of fraud detection related to the financial account, downloadinga second token representing a second payment method associated with thefinancial account; and at the dynamic transaction card: downloading thesecond token from the mobile computing device via the wirelessconnection; generating a second magnetic stripe sequence commandrepresenting the second cryptogram and the second token; and in responseto detecting a second magnetic stripe card reader proximal the magneticstripe emulator, driving the magnetic stripe emulator according to thesecond magnetic stripe sequence command.
 13. A method comprising: at anative application executing on a mobile computing device: receiving afirst token from an external token generator generated on behalf of afinancial institution; and storing the first token in local memory onthe mobile computing device, the first token representing a firstpayment method associated with a financial account; at a first time,accessing a first cryptogram; at a second time, establishing a wirelessconnection with the mobile computing device; and at the dynamictransaction card: detecting a signal, output by a piezoelectrictransducer arranged within the dynamic transaction card, that exceeds apreset threshold magnitude, the piezoelectric transducer configured tooutput a signal corresponding to a degree of deflection of the dynamictransaction card; in response to detecting the signal, activating thedynamic transaction card at approximately the second time; in responseto activation of the dynamic transaction card, transmitting a query fora token to the mobile computing device over the wireless connection;downloading the first token from the mobile computing device; generatinga first magnetic stripe sequence command representing the firstcryptogram and the first token; and in response to detecting a magneticstripe card reader proximal a magnetic stripe emulator integrated intothe dynamic transaction card at a third time succeeding the second time,driving the magnetic stripe emulator according to the first magneticstripe sequence command.
 14. The method of claim 13, further comprising,at the native application: downloading the first token and a graphicalrepresentation of a first payment method associated with a financialaccount hosted by the financial institution; and rendering the graphicalrepresentation of the first payment method within the native applicationto indicate activation of the first payment method within the financialaccount.
 15. The method of claim 13, further comprising: whereinreceiving the first token at the native application comprises receivinga group of tokens from the external token generator, the group of tokenscomprising the first token and a second token distinct from the firsttoken; further comprising, at a fourth time succeeding the third time:at the dynamic transaction card, transmitting a second query for a tokento the mobile computing device at approximately the third time inresponse to activation of the dynamic transaction card; downloading thesecond token from the mobile computing device; generating a secondmagnetic stripe sequence command representing the first cryptogram andthe second token; and in response to detecting a second magnetic stripecard reader proximal the magnetic stripe emulator at a fifth timesucceeding and within a threshold duration of the fourth time, drivingthe magnetic stripe emulator according to the second magnetic stripesequence command.
 16. The method of claim 15, further comprising: at thedynamic transaction card, transmitting confirmation of emulation of thefirst token at the magnetic stripe emulator to the mobile computingdevice in response to driving the magnetic stripe emulator according tothe first magnetic stripe sequence command; and at the nativeapplication, deleting the first token from local memory in response toreceiving confirmation of emulation of the first token from the dynamictransaction card.
 17. The method of claim 13, further comprising, at anative application executing on the mobile computing device, in responseto receiving confirmation of receipt of the first token from the dynamictransaction card, deleting the first token from local memory on themobile computing device.
 18. The method of claim 17, further comprising,at the dynamic transaction card, in response to passage of a thresholdduration of time following the third time, deleting the first token fromthe dynamic transaction card.
 19. A method comprising, at a dynamictransaction card: at a first time, accessing a first cryptogram; at asecond time, establishing a wireless connection with a mobile computingdevice; in response to establishing the wireless connection with themobile computing device, accessing a first token associated with thefirst cryptogram; generating a first magnetic stripe sequence commandbased on the first cryptogram and the first token representing a firstpayment method; in response to detecting a magnetic stripe card readerproximal a magnetic stripe emulator integrated into the dynamictransaction card at a third time succeeding the second time, driving themagnetic stripe emulator according to the first magnetic stripe sequencecommand in a first transaction; at a native application executing on themobile computing device, downloading a second payment method; at thedynamic transaction card: downloading a second magnetic stripe sequencecommand representing the second payment method from the mobile computingdevice via the wireless connection; storing the second magnetic stripesequence command in local memory of the dynamic transaction card; and inresponse to failure of the first transaction at a POS system and inresponse to detection of the magnetic stripe card reader proximal thedynamic transaction card within a threshold duration of the third time,driving the magnetic stripe emulator according to the second magneticstripe sequence command in a second transaction; and at the nativeapplication: recording a first location associated with the firsttransaction; receiving transaction information from the dynamictransaction card identifying failure of the first transaction; andgenerating a map identifying security preferences of the POS systembased on the first location and the transaction information.